Client device with video playlist translation via client-side proxy and methods for use therewith

ABSTRACT

A client device includes a client-side proxy that is operable to receive server playlist data corresponding to the selected one of the plurality of video programs, to generate proxy playlist data corresponding to the selected one of the plurality of video programs based on the server playlist data and to send the proxy playlist data to the video player. In particular, the client-side proxy generates the proxy playlist data by translating the server playlist data from a first playlist format, such as a sliding window format of the HLS protocol, to a second playlist format, such as an event playlist format.

CROSS REFERENCES TO RELATED APPLICATIONS

The present application claims priority under 35 U.S.C. 119 to the provisionally filed application entitled, VIDEO SERVER, CLIENT DEVICE AND METHODS FOR USE THEREWITH, having application Ser. No. 61/735,796, filed on Dec. 11, 2012; the contents of which are incorporated herein by reference thereto.

TECHNICAL FIELD OF THE INVENTION

The present invention relates to servers and client devices used for streaming media applications, including video on demand.

DESCRIPTION OF RELATED ART

The number of households having multiple television sets is increasing, and many users want the latest and greatest video viewing services. As such, many households have satellite receivers, cable set-top boxes, and televisions, et cetera, that provide access to broadcast video services. For in-home Internet access, each computer or Internet device can have its own Internet connection. As such, each computer or Internet device includes a modem. As an alternative, an in-home wireless local area network may be used to provide Internet access and to communicate multimedia information to multiple devices within the home. In such an in-home local area network, each computer or Internet device includes a network card to access an IP gateway. The gateway provides the coupling to the Internet. As an alternative to broadcast video, the Internet provides access to streaming video services. Instead of broadcasting all programming to every customer, each customer receives only those programs that they want, when they want them.

One of the most common ways of streaming continuous video over the Internet today is through the use of the “HTTP Live Streaming” (HLS) protocol. It is developed by Apple Corporation and supported in most of Apple's devices. The HLS protocol operates on a streaming server that uses a standard HTTP (Hypertext Transfer Protocol) web server component. A video encoder takes a source video and encodes it at different bitrates intended for use in different network conditions (high or low capacity) and with different playback devices. The stream is a Motion Picture Expert Group (MPEG2) transport stream divided into multiple segments. Each segment is a compressed piece of the original video of several seconds length. If a segment length is 10 seconds, a one hour movie could be streamed in 360 segments. The segments, put together, form the stream and include the bits from the binary compressed version of the content. Each segment is downloadable over HTTP and accessible via URL. In operation, a client device that wishes to play a streaming video requests and downloads each segment of the stream via separate URL. The segments are decoded by the client device in sequence to play the stream.

A text file with the list of the segment's URLs is called a playlist. A simple playlist can appear as follows:

  http://myserver.com?segid=100 http://myserver.com?segid=101 http://myserver.com?segid=102 http://myserver.com?segid=103 http://myserver.com?segid=104 #EXT-X-ENDLIST where each line is a segment's URL and #EXT-X-ENDLIST is an indication of the end of the stream. There are different types of playlists. An Already Recorded Show Playlist is created, when the server has the entire show from the beginning to the end. This type of playlist contains list of URLs for all segments and terminated with #EXT-X-ENDLIST tag, indicating that there will be no segments after that point for this stream. The client assumes that all segments are accessible at all times, and could be requested in any order at any moment. This type of play list allows the client to start playback at any random position at the stream, and jump back or forward.

Another form of playlist is a Sliding Window Playlist. This type of playlist is used for live translation/encoding. The playlist contains only a limited number of segments without the termination tag. The client is only able to request segments from this list, without seeing the entire stream. Upon receiving the last segment from the last playlist the client sends request for another playlist expecting to get list of segments beyond the last one it just played back. At the end of the content the server publishes a playlist with an #EXT-X-ENDLIST tag present, informing the client that the current playlist is the last playlist. Because the client has limited visibility to the stream, this type of playlist doesn't allow the client to perform any trick operation on the stream. Moreover, the client is not even informed about the total length of the stream. An example of a Sliding Window Playlist is presented below:

  Playlist #1 http://myserver.com?segid=100 http://myserver.com?segid=102 http://myserver.com?segid=103 Playlist #2 http://myserver.com?segid=104 http://myserver.com?segid=105 http://myserver.com?segid=106 Playlist #3 http://myserver.com?segid=107 http://myserver.com?segid=108 http://myserver.com?segid=109 #EXT-X-ENDLIST

In this example, the client requests Playlist #1, after playing back segment 103 it sends request for another playlist, receiving Playlist #2. After playing back segment 106 it sends request for another playlist, receiving Playlist #3. The playback is done when the client plays last segment from the Playlist #3 and encounters the termination tag.

A further type of playlist is an Event Playlist that is designed for broadcast live events. It has only one playlist, which contains list of the segments from the beginning of the content to the current moment. Whenever a new segment is available it is added to the bottom of the list. The end of list termination tag added as the last line when the event is over. In operation, every time the client reaches the end of current playlist and doesn't encounter a termination tag it requests a new playlist from the server. The event playlist enables the client to perform trick play on the already encoded portion of the content, though, the total length of the program is not available. As the playlist keeps growing over time the amount of traffic and load on the server is getting bigger. By the end of the program the client receives the entire playlist—1200 lines long for a one hour movie with 3 second segments.

One feature of the HLS standard is support for streaming of content with adaptive bitrate. Bitrate is a property of the video stream measured in bits per second. It represents the number of bits in one second of the media file. Higher bitrate streams are bigger, but have better quality. Lower bitrate streams are smaller, and although they have poor quality, because of the small size they could be transferred to the client much faster. The bitrate is chosen by the client depending on the quality of the network connection. At any time during streaming, the client, depending on the network bandwidth at the moment, may switch to a different bitrate. The new bitrate could be either higher or lower than the current one.

HLS implements adaptive bitrate support by introducing a variant playlist. It is a master playlist with a list of URLs pointing to regular playlists files, described above. Each URL is a reference to a playlist of a particular bitrate. Below is an example of a variant playlist:

#EXTM3U #EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=620000 http://myserver.com/hls/movie/620kb/prog_index.m3u8 #EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=320000 http://myserver.com/hls/movie/320kb/prog_index.m3u8 This variant playlist refers to two regular playlists; the first is for 620 kb/sec content and the second is for 320 kb/sec. At the beginning of a program, the client downloads and parses the variant playlist. The client assumes that segments of all bitrates listed in the variant playlist are accessible at any time. If, for example, the client is experiencing a good network connection, the client may decide to start playback with the highest available bitrate, which is 620 kb/sec in the case above. The client gets the playlist for this bitrate using the URL listed in variant playlist:

http://myserver.com/hls/movie/620kb/prog_index.m3u8

The client parses the playlist and starts downloading of the segments one by one. If, during downloading of a segment with id=103, the network signal got weaker, the client may not be able to fetch the segment fast enough. In this case the client may fall back to a lower bitrate 320 kb/sec. The client discards the partially downloaded segment with id=103, and starts downloading segments from the lower bitrate playlist starting from the segment with id=103.

An advantage of HLS streaming is that the server is a standard web server. Beyond the application-specific tools needed for segmentation and playlist generation, the software and infrastructure comprises of standard and freely available components that are often already in place. The limitations and disadvantages of HLS and other conventional and traditional approaches will become apparent to one of ordinary skill in the art through comparison of such systems with the present invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 presents a pictorial representation of a content distribution system that in accordance with an embodiment of the present invention.

FIG. 2 presents a block diagram representation of streaming server 50 in accordance with an embodiment of the present invention.

FIG. 3 presents a block diagram representation of playlist data 112 in accordance with an embodiment of the present invention.

FIG. 4 presents a block diagram representation of variant playlist data 114 in accordance with an embodiment of the present invention.

FIG. 5 presents a block diagram representation of an encoder 104 in accordance with an embodiment of the present invention.

FIG. 6 presents a block diagram representation of a rate data generator 220 in accordance with another embodiment of the present invention.

FIG. 7 presents a block diagram representation of streaming server 50′ in accordance with an embodiment of the present invention.

FIG. 8 presents a block diagram representation of an encoder 104 in accordance with an embodiment of the present invention.

FIG. 9 presents a temporal diagram representation of program segments in accordance with an embodiment of the present invention.

FIG. 10 presents a block diagram representation of segment playlist data 250 in accordance with an embodiment of the present invention.

FIG. 11 presents a block diagram representation of segment playlist data 252 in accordance with an embodiment of the present invention.

FIG. 12 presents a block diagram representation of a client device 300 in accordance with an embodiment of the present invention.

FIG. 13 presents a block diagram representation of a client-side proxy device 308 in accordance with an embodiment of the present invention.

FIG. 14 presents a flowchart representation of a method in accordance with an embodiment of the present invention.

FIG. 15 presents a flowchart representation of a method in accordance with an embodiment of the present invention.

FIG. 16 presents a flowchart representation of a method in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION INCLUDING THE PRESENTLY PREFERRED EMBODIMENTS

FIG. 1 presents a pictorial representation of a content distribution system in accordance with an embodiment of the present invention. In particular, a streaming video server 50 is capable of accessing and distributing content from one or more video sources 40 to a plurality of client devices such as a television 60, smart phone, internet tablet or other personal media players 62 and 64, handheld video player 66, and personal computer 68. While specific client devices are shown, video server 50 is capable of accessing and distributing content from one or more video sources 40 to other client devices that can receive and reproduce media content.

The streaming video server 50 uses an on-demand encoding process and a virtual file system. In an embodiment of the present invention, the streaming video server 50 allows adaptable bitrates to be supported with reduced requirements for persistent storage. The streaming video server 50 accesses a virtual file system containing the files needed for streaming: variant playlist files, playlist files, content encryption keys, and video segment files. Most of the video data in the file system is not stored in a real non-volatile storage device; instead the data may be generated only when necessary due to a read operation in request for particular video content from a client device.

In the example shown, the video source or sources 40 are external to the system and coupled to the streaming video server 50 to provide coded audio-video streams via a secure channel, such as a secure socket layer (SSL) connection, a private network, a virtual private network or other secure connection. The video source or sources 40 can have two types of content: live and pre-recorded. The video source 40 can be a live video source such as a broadcast cable network, a broadcast satellite network, a broadcast television network, an IP television distribution system, a broadcast mobile network, a video conferencing service or other source of live video. Example of video sources 40 of prerecorded content include a video on demand source such as a YouTube, Hulu, Netflix, or other streaming video source, a cable or IP television video on demand network, a digital video recorder, UPnP media server, camcorder, personal computer or other source of stored video. The two types of content can be handled differently when limited network bandwidth causes the rate of data transfer to the client to be lower than the encoding rate. For live content, the streaming system discards portions of the audio-video stream that could not be transferred within some time limit. This ensures that the delay between transmission at the source, and decoding and playback at the client is bounded. For a video conference, this means that conversations will not be hampered by excessive delays, but there may be discontinuities in the conversation when the network slows suddenly. Pre-recorded content can be streamed in a continuous manner. If the network slows suddenly and the client runs out of data to decode, it handles this in the short term by waiting for more data, and in the longer term by selecting a variant playlist with a lower bitrate.

In operation, the streaming video server 50 transcodes or decodes and re-encodes the content from a video source 40 to the bitrates corresponding to the playlists. In this fashion, encoding of a video program is performed only when it is needed in response to a client's request for that particular program. Therefore, videos that are made available by the streaming video server 50, but never requested by the client, do not incur the overhead of encoding.

When streaming is initiated, a video encoder of streaming video server 50 is allocated for the session. The encoder outputs a continuous audio-video bitstream and then a post-processing step breaks the streaming into the required segments. In addition, the encryption key generation process can be performed on-demand. This allows the keys to not be saved to a storage device, protecting the security of the key from being read without authorization. For increased content security, the keys can be generated randomly and are never used for more than one streaming session. The encryption process can also be performed on-demand.

In operation, the streaming video server 50 produces segments in-order, i.e. 100, 101, 102 and so on. This works well if the requests from the client come in order. However, every request out of order requires repositioning in the input stream and therefore restarts the transcoder from this new position. This action takes can lead to a delay of 10-20 seconds. If HLS bitrate control were implemented as per specification, each change of bitrate by the client would result in a request of an out of order segment, leading to a delay. Further, each delay could make the client to think that there is not enough network bandwidth, and the client could respond by lowering the bitrate even more. Ultimately, this could result where the client continues to switch the bitrate until the lowest possible bitrate is reached.

To address this issue, the streaming video server 50 presents a variant playlist that indicates only a single bitrate, i.e. a single variant (a single entry on the list—as opposed to multiple bit rate choices). This eliminates attempts at rate control from the client side. Instead, the streaming video server 50 measures the network bandwidth on the server side, and adjusts the bitrate of the generated video stream according to the current network conditions. As the client doesn't perform any bitrate control, it never sends an out-of-order request, and the transcoder is never restarted during bitrate adjustment.

Streaming video server 50 can further include one or more features of the present invention described further in conjunction with FIGS. 2-16 that follow.

FIG. 2 presents a block diagram representation of streaming server 50 in accordance with an embodiment of the present invention. As shown, streaming video server 50 includes a command handler 100, one or more video encoders 104 and video encryptors 106, and an encryption key generator 108. Streaming video server 50 also includes virtual file system 110 that stores playlist data 112 that includes a content index corresponding to the video programs available from the video source or sources 40 as well as a segment playlist for each video program that includes a list of addresses for each segment of that video program. Virtual file system 110 further stores variant playlist data 114 that indicates a single entry for streaming each of the plurality of video programs. The URIs in the content index, variant playlist, and segment playlist may or may not correspond to actual files as in a traditional web server or streaming server that serves files stored on hard drive. These addresses are generated by the streaming video server 50 and recognized as references to the virtual files when the client makes the HTTP request for a particular video program. This applies to the URIs for the lists themselves and also for the encrypted segment data and encryption keys. When a request is received for a “file” in the virtual file system, the server generates the appropriate response depending on the actual request. For example, (a) responding with the content index, variant playlist, segment playlist data using information stored in memory, (b) generating a random encryption key, storing it to memory (for subsequent segment requests), and sending it in the response to the client, (c), initiating video transfer from a source, initiating the encoding and segmentation, sending the first segment in the response to the client, (d) for a previously initiated transfer, encoding, segmenting, and return the next segment to the client.

A network interface 102 is included to bidirectionally communicate with at least one client device via network 30 and to bidirectionally communicate with the at least one video source, such as via a secure channel of network 30 or another network. The network interface 102 can include a modem, transceiver or other network interface adaptor that implements a serial or parallel connection such as an Ethernet connection, Universal Serial Bus (USB) connection, an Institute of Electrical and Electronics Engineers (IEEE) 1394 (Firewire) connection, small computer serial interface (SCSI), high definition media interface (HDMI) connection or other wired connection that operates in accordance with either a standard or custom interface protocol. In addition or in the alternative, the network interface 102 can include a wireless link for coupling to the network 30 and/or video source or sources 40 either directly or indirectly through one or more devices that operate in accordance with a wireless network protocol such as 802.11a,b,g,n (referred to generically as 802.11x), Bluetooth, Ultra Wideband (UWB), 3G wireless data connection, 4G wireless data connection or other wireless connection that operates in accordance with either a standard or custom interface protocol.

In operation, the command handler 100 coordinates the encoding and encryption processes with a client's requests for video content. For example, the command handler 100 receives a HTTP request for a selected one of the plurality of video programs from the at least one client device via the network interface 102. In response to the request, the selected one of the plurality of video programs is retrieved from the video source or sources 40, via the network interface. For example, the command handler can access the playlist data 112 to determine the universal resource identifier (URI) or other address for retrieving the selected one of the plurality of video programs from the video source or sources 40.

The command handler 100 retrieves the selected one of the plurality of video programs. A plurality of encoded segments are generated from selected video program, via a video encoder 104, at a selected bit rate. The video encoder 104 can include one or more encoders or transcoders that receive an encoded video program from the video source or sources 40 and that decodes and re-encodes or otherwise transcodes the audio and/or video of the program into the scale, resolution, and digital compression format, and at the selected bitrate for the requesting client device. In particular, the video encoder 104 can operate in accordance with a motion picture expert group (MPEG) format such as MPEG2, MPEG4 part 10, also referred to as H.264. Other video formats such as VC1, digital video (DV), etc., could likewise be employed. In an embodiment of the present invention, the video source or sources 40 contain unsegmented videos. Upon the client request of the first segment for a particular video and bitrate, the streaming video server 50 starts the retrieval of the video from the corresponding video source 40, and performs the encoding and segmentation. The segmentation can be done before or after the encoding, though it can be more practical to do the encoding first, then the segmentation.

Encrypted segments are generated from the encoded segments, via the video encryptor 106, based on an encryption key. The encrypted segments are then stored as video segments 116 that are then sent, via the network interface 102, as a streaming video signal to the at least one client device that requested the video program. The video encryptor 106 can operate in accordance with one or more cryptography algorithms such as data encryption standard (DES), Rivest, Shamir, Adelman (RSA), elliptical curve cryptography (ECC), Advanced Encryption Standard (AES) or other algorithm.

Streaming server module 50 includes an encryption key generator that generates the encryption key in response to the request. As discussed in conjunction with FIG. 1, the encryption key generator 108 generates encryption keys on-demand. This allows the keys to not be saved to a storage device, protecting the security of the key from being read without authorization. For increased content security, the keys can be generated randomly and are used for only one streaming session. In theory, while identical encryption keys could reoccur randomly, each encryption key is nevertheless practically or substantially unique to the request.

In an embodiment of the present invention, the rate data generator 220 generates rate data that indicates the selected bit rate. In operation, the rate data generator selects the bit rates based on channel information from network 30 pertaining to a communication channel between the network interface and the client device that generated the request. The channel information can include network bandwidth data, network utilization data, and/or other data including a channel type, expected bit rate, current actual bit rate, etc. As the bit rate is adjusted, the video encoder 106 encodes each current segment at the selected rate.

The command handler 100, video encoder 104, video encryptor 106, encryption key generator 108 rate data generator 220 and virtual file system 110 can be implemented via one or more processing devices and one or more memory devices. Such processing devices can include a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on operational instructions that are stored in a memory. The memory can include a hard disc drive or other disc drive, read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing device implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry.

The streaming video server 50 has additional advantages over convention servers. The requirements for storage are reduced for the video segments, variant playlist, and playlists. This is especially important for embedded systems with limited storage capabilities. In addition, since the encryption process is performed on-demand like the encoding process, the key can be protected such that it can be accessed only by the intended client device, as opposed to all potential clients. Furthermore, the key itself can be changed while streaming is in progress, and this decision can be made during run-time as needed. These content protect features are especially important for premium content such as pay-per-view video. Further, the risk of unauthorized access to unencrypted video streams is reduced since they are never stored in encrypted or unencrypted form to a persistent storage device where they may be accessed by attackers. Also, live and pre-recorded video content can be handled differently. Streams from live sources will not suffer large delays.

FIG. 3 presents a block diagram representation of playlist data 112 in accordance with an embodiment of the present invention. FIG. 4 presents a block diagram representation of variant playlist data 114 in accordance with an embodiment of the present invention. In the example shown, playlist data 112 includes content index 120 a title of all available video selections from any of video sources 40, and a URI address for accessing the variant playlist data 114 for each program. The content index does not have to be in a particular format, as long as the client devices and the streaming video server 50 use the same format or the formats can be translated to be compatible. Example formats include JSON, XML, plain text, etc. Other address formats could likewise employed including a file addressing scheme, an IP address, or other logical or physical addressing. In addition, the while specific video on-demand programs are presented, as previously discussed, live video programming could be retrieved, segmented, encoded and encrypted on demand for delivery in response to a client request.

In addition, playlist data 112 includes a segment playlist 122 for each video program and for each bitrate. Each segment playlist includes a segment number and address for each segment of the video program and optionally an address of an encryption key used for encrypting that particular segment. Again, while URIs are shown, Other address formats could likewise employed including a file addressing scheme, an IP address, or other logical or physical addressing.

The virtual file system also contains variant playlists for each video program in the content index. Each variant playlist includes an address (such as the URI shown) for the segment playlists, which are also contained in the virtual file system with a single entry.

In one example of operation, the streaming video server maintains playlist data 112 that includes a content Index that is served to the client upon its request. The streaming video server 50 can, for example, query each of the video sources 40 or its list of videos, then aggregate them to the create such a content index. The content index contains, for each item, the URI of the variant playlist. The client selects one item (e.g., via user input), then makes the HTTP request for the URI corresponding to that variant playlist for that item. The variant playlist contains the segment playlist URI for a single “phantom” bitrate, as shown in FIG. 4. As discussed in conjunction with FIG. 1, this forces the client to choose the single variant entry and eliminates the adaptation of the bit rate from the client side—in lieu of the server side adaptation of the bit rate. The client makes an HTTP request for the playlist (the only item on the list). The segment playlist contains the URIs for each segment's data and each segment's encryption key.

The URIs in the content index, variant playlist, and segment playlist do not correspond to actual files as in a traditional web server or streaming server that serves files stored on hard drive; the URIs are generated by the server and recognized as references to the virtual files when the client makes the HTTP request. This applies to the URIs for the lists themselves and also for the segment data and encryption keys. When a request is received for a “file” in the virtual file system, the server generates the appropriate response depending on the actual request. For example, (a) responding with the content index, variant playlist, segment playlist data using information stored in memory, (b) generating a random encryption key, storing it to memory (for subsequent segment requests), and sending it in the response to the client, (c), initiating video transfer from a source, initiating the encoding and segmentation, sending the first segment in the response to the client, (d) for a previously initiated transfer, encoding and segmentation, return the next segment to the client. As shown the variant playlist data includes only a single entry for a particular title, a group of titles, for all programs from a particular video source 40 or from all video sources.

The streaming video server 50 provides additional advantages over a conventional HLS-based server system. Multiple video encoders 104 can be present in order to meet the simultaneous use requirements of on-demand transcoding for multiple client devices. The encoded data is generated on as-needed basis and reducing the need for persistent storage. Encryption keys can be generated on an as-needed basis and never stored except temporarily in volatile memory, also saving storage. By not storing encoded data and encryption keys, content security is improved. Also, live and pre-recorded content can be handled differently, resulting in improved user experience.

A conventional HLS-based server system must store the video for all bitrate settings. The requirement for storage capacity grows with the number of bitrate settings and duration of the video. The data must be stored even though it may never be requested by the client, because it can't be absolutely determined at encoding time which particular segments will be used by the clients. In the present system, the data resulting from video transfer from a video source 40, encoding, key generation, and encryption are not stored to persistent storage (e.g. a hard drive). Transfer, encoding, segmentation, and encryption on a source video can be deferred until that video is requested by the client.

In addition, in a conventional HLS-based server system, the bitrates for the video must be set before the encoding process starts. Some knowledge of the expected network capacity and playback device types is required in order to select the appropriate bitrates. Typically, three bitrates are used: one low bitrate setting of approximately 64 kbps, and two higher settings between 100 and 500 kbps. Setting the bitrates at encoding time means that the target use cases are also set. Any unexpected cases (e.g., very high network capacity, a new client device) are not addressed. When the video segments are encrypted, an encryption key must be selected that is to be used by all clients.

In contrast, the streaming video server 50 can employ adaptive bitrates without having to encode and store the encoded and encrypted video segments for an entire program at all of those bitrates prior to streaming. In an embodiment of the present invention, prior to streaming, little needs to be known about the client device and the possible network conditions. In addition, since bitrate settings are adjusted to adapt to current conditions adjustments and generated on the fly, these adjustments can be made with a fine granularity over the full range required. This reduces the distracting effect of the video and audio quality changing greatly from one segment to the other due to a large change in bitrate. More importantly, the adaptive bitrate feature allows the network usage to be optimized for the current conditions. That is, it is more likely that the selected bitrate is the maximum allowed by the network connection between the server and client, thus maximizing the video and audio quality for the end user.

FIG. 5 presents a block diagram representation of an encoder 104 in accordance with an embodiment of the present invention. In this embodiment, the video encoder 104 encodes the selected video program 200 into encoded video program segments 204. Video encryptor 106 encrypts the encoded video programs segments 204 into encrypted video program segments 206 based on an encryption key, such as a key from encryption key generator 108. The encrypted video program segments 206 are transmitted over network 30 via network interface 102. In operation, rate data generator 220 generates rate data 222 based on transmission feedback data 224 from the network interface 102 that reflects the channel conditions. Transmission feedback data 224 can also include data from the client device 60, 62, 64, 66 or 68 that indicates information regarding that client device. Examples of such client data includes a current one of a plurality of device states, such as a client device operating system, video display window size (minimized, partial or full screen) or a volume setting that can be used to adjust the video resolution, or audio encoding depth, the number of audio channels or be used to decide whether to or not to include audio information in the stream. The rate data 222 can also be optionally based on context data 202 that relates to the content of the video program 200. The context data 202 can indicate information derived from the video program 200 or the video source 40 such as the genre of video (e.g., news, sit com, music, cartoon, video conference), the number of audio channels and/or other information regarding the characteristics, properties or format of the video program 200.

The video encoder 104 encodes the video program segments based on one or more encoding parameters that are adjusted in response to rate data 222 that relates to the streaming session for the selected video program.

As discussed in conjunction with FIG. 2, video encoder 104 can operate in accordance with a motion picture expert group (MPEG) format such as MPEG2, MPEG4 part 10, also referred to as H.264. Other video formats such as VC1, digital video (DV), etc., could likewise be employed. In an embodiment of the present invention, the video program 200 can be segmented before or after encoding. Video encoder 104 can be implemented via one or more processing devices and one or more memory devices. Such processing devices can include a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on operational instructions that are stored in a memory. The memory can include a hard disc drive or other disc drive, read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing device implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry.

In operation, the streaming server 50 responds to the segment requests by encoding the source content at the selected bitrate. The encoding process is performed on-demand, therefore the encoding parameters can be adjusted to conform with the rate data 222 that reflects the conditions of the current streaming session. In response to the rate data 222, the video encoder 104 can adaptively choose or otherwise adjust the overall average bitrate of a segment, and for a selected overall average bitrate, the average bitrate of the audio content and the average bitrate of the video content. In addition, the video encoder 104 can adaptively choose or otherwise adjust other encoding parameters such as the output video resolution, the output video frame rate, the number of encoded audio channels, etc.

FIG. 6 presents a block diagram representation of a rate data generator 220 in accordance with another embodiment of the present invention. In particular, rate data generator 220 includes a rate data processor 230 that operates based on transmission feedback data 224 and optionally based on context data 202 to generate rate data 222. The rate data processor 230 can be implemented via one or more processing devices and one or more memory devices. Such processing devices can include a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on operational instructions that are stored in a memory. The memory can include a hard disc drive or other disc drive, read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing device implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry.

In an embodiment, the rate data processor 230 operates based on transmission feedback data 224 that includes network bandwidth data 226 and network utilization data 228. Network bandwidth data 226 represents a number of bytes per second transferred over the network connection. For example, this quantity can be calculated based on an average number of bytes sent to the client in the last 15 seconds. It can be measured in bytes per second and calculated as a running average such as an unweighted average, an exponentially weighted moving average, a filtered average or other mean, median or other average. Network utilization data 228 can be calculated based in the percentage of time spent in data transmission in a particular second—i.e. what part of that second the network interface 120 was busy with sending data to network 30. For example, this quantity can be calculated based on by measuring the amount of time spent in a socket write( ) function during each second. Spending 500 ms of a particular second in writing data to the channel yields a 50% utilization.

The rate data 222 can be calculated based on the value of the variable “bitrate” in the following algorithm.

   if ( aUtilization < mTargetUtilization )  {   // try to speed-up   if ( aUtilization < 10 )   {    // less than 10% utilization is not reliable, try to use double rate than the current speed    bitrate = aSpeed * 2;   }   else   {    realSpeed = aSpeed * 100 / aUtilization;    bitrate = realSpeed * mTargetUtilization / 100;   }  }  else  {   // try to slow down   bitrate = aSpeed * mTargetUtilization / aUtilization;  } where aUtilization and aSpeed are current network utilization (network utilization data 228) and current network speed (network bandwidth data 226) and mTargetUtilization is a maximum percentage of the total reachable bandwidth which could be used for transmission streaming data. Reserving some amount to account for errors in bitrate calculation, and for different overheads such as HTTP headers etc., mTargetUtilization can be set at 90% or other limit.

In addition, to the algorithm above, the rate data processor 230 can adjust the data rate 222 based on a minimum data rate. In particular, the HLS protocol prohibits changing of any parameters of the stream. Particularly, if the stream contained both video and audio, each of its segments of any bitrate should always contain both video and audio disregarding of how low the bitrate is. Moreover, the audio parameters, including the bitrate, stay the same for all bitrates for current stream. Therefor the lowest reachable bitrate may be limited based on the bit rate required to send the audio track. As the video track couldn't be completely removed, in an embodiment, to get as close to the audio bitrate as possible, the encoded video program segments can be replaced with a still image of the video program 200, a standard still image or other still image. A bitrate of such a video stream should be close to zero, which makes the total bitrate of the stream equal to audio bitrate.

At the beginning of a video program, the rate data generator can adjusts the data rate 222 based on an initial data rate that starts the stream at the first segment. The initial data rate can be fixed as a nominal data rate, estimated based on partial transmission feedback data 224 and/or generated based on context data that indicates properties of the selected one of the plurality of video programs.

While the rate data 222 can be generated as described above, other techniques can likewise be employed. The rate data 222 be generated based on a bandwidth assessment or other bandwidth test performed in response to the request for the selected video program 200. A channel bandwidth test can be performed prior to transmission of the first segment. For example, prior to requesting the first segment, the client device 60, 62, 64, 66 or 68 can request a URI that is specifically used to perform the channel bandwidth test. The streaming server 50 recognizes this request and responds with a test signal to the requesting client device. The transfer rate of the test signal can be measured by the streaming server 50. For example, the response to the variant playlist request can be padded with content that is to be ignored by the requesting client device (normal variant playlist content still exists). This can be done by placing whitespace characters at the end, or inserting lines that start with the comment character ‘#’. The amount of data can be chosen so the total size of the variant playlist is suitable for a channel bandwidth test while reducing the time delay in starting the playback of the selected video program to the user. Using too much data could slow the user experience, while using too little data could reduce the accuracy of the test result. The transfer rate of the variant playlist is measured by the streaming server 50.

FIG. 7 presents a block diagram representation of streaming server 50′ in accordance with an embodiment of the present invention. In particular, a streaming server 50′ is presented that operates in a similar fashion to streaming server 50 and that includes many similar elements to streaming server 50 that are referred to by common reference numerals. Streaming server 50′ includes a segment memory 240 that includes one or more initial video program segments for each title in the content index that can be used to initialize the video stream when the first video segments are being produced. This reduces the latency period of the stream—speeding up the time to transmission of the first segments since there is no need to wait for encoding or transcoding—these initial segments can be retrieved directly from the segment memory. Further details of this configuration including optional functions and features will be described in conjunction with FIGS. 8 and 9 that follow.

FIG. 8 presents a block diagram representation of an encoder 104 in accordance with an embodiment of the present invention. A similar structure is presented to FIG. 5 that includes many similar elements that are referred to by common reference numerals. This configuration includes a segment memory 240 that stores one or more stored initial video program segments for each video program in the content index. When a particular video program 200 is requested, the initial segment or segments of the stream can be retrieved from the segment memory 240 as stored initial program video segments 242 that are passed by multiplexer 244 to video encryptor 106. At the same time that these stored initial video program segments 242 are being retrieved, the video encoder 104 can begin encoding or transcoding the video program 200 to generate encoded video program segments 204. In an embodiment, the video encoder 104 begins the production of encoded video program segments 204 at a point in time before a request for the corresponding segment arrives. In this fashion, if/when the request for the segment arrives, the video encoder 104 is prepared. In this configuration, a buffer of the video encoder 104 (not expressly shown) is used to store the encoded video segment 204.

The multiplexer 244 can switch the stream from the stored initial video program segments 242 to the encoded video program segments 204 when the stored initial video program segments 242 are exhausted. In other mode of operation, the multiplexer 244 can switch the stream from the stored initial video program segments 242 to the encoded video program segments 204 when the first encoded video program segments 204 is complete and corresponding prior segment from the stored initial video program segments 242 has been passed to the video encryptor 106.

FIG. 9 presents a temporal diagram representation of program segments in accordance with an embodiment of the present invention. In particular, a plurality of segments (001-009) of a video program that are output from the multiplexer 244 are shown. In this example when a request for a first segment (001) of a particular video program arrives the video encoder 104 begins the production of encoded video program segments 204 beginning at segment (004)—at a point in time before a request for the segment (004) arrives. The multiplexer 244 begins feeding the first three segments (001-003) of the video program as the stored initial video program segments 242 during the time the encoder 104 is initializing. By the time the last stored segment (003) is passed to the video encryptor 106, the next segment (004) is ready from the video encoder 104 and when a request for the segment (004) arrives, the multiplexer 244 can switch to the encoded video program segments 204.

In the example shown, the multiplexer 244 generates output segments to the video encryptor as the initial video program segments (001-003) during an initial latency period of the video encoder in producing a first encoded video segment (004)—the next segment in a temporal sequence of the video program segments. Said another way, the initial video program segments (001-003) cover an initial temporal period of a selected video program corresponding to an initial latency period of the video encoder 104 in producing a first segment of the encoded video segments (004).

The number of stored initial program segments 242 can be selected based on their duration to cover or more than cover any such latency period. In the example described above, segments (004-005) may also be stored in the segment memory 240 for use if necessary, depending on the selected encoding bit rate. If a video segment is requested by the client device that has already been encoded and the corresponding stored initial video program segment has not been sent, the multiplexer 244 can switch to sending the encoded video program segment corresponding to the request in lieu of the stored initial video program segment of this number.

It should also be noted that transmission feedback data 244 can be generated during the transmission of the stored initial video program segments in order to more quickly generate meaningful rate data 222.

FIGS. 10 and 11 present block diagram representations of segment playlist data 250 and 252 in accordance with an embodiment of the present invention. In particular, playlist data is presented for use in conjunction with streaming video server 50 or 50′ in situations where a client has bookmarked a position in a streaming video. Bookmarking is a possibility of starting a new streaming session from the point where the client stopped watching this particular video at the last time. For example, a position in a streaming video can be bookmarked by either a client device or a streaming video server 50 or 50′ in response to the client device stopping or pausing a video stream or otherwise by a client device indicating a bookmark position in the video program that the client device would like to return to at some later time. In HLS, bookmarking is implemented by receiving the bookmark position from a streaming device via the command channel, and then instructing the video player to start the playback from this particular position.

The resumption process could be explained by the following pseudo-code:

1 Time bookmark=server.getBookmark( );

2 Player player=new Player( );

3 player.startStream(“http://myserver.com?myplaylist.m3u”);

4 player.seek(bookmark);

On some client device platforms, such as Apple device platforms, the video player first starts playback at line 3. However, the video player sends a request for a segment at bookmark position to resume playback, but only after requesting one or more segments from the beginning of the stream. This can lead to a server such as streaming video server 50 or 50′ being initialized twice; first for the beginning of the stream, and the second time for the bookmark position.

The streaming video server 50 or 50′ can address this issue by starting the video player from the bookmark position, without explicitly passing the bookmark. In operation, the command handler 100 receives a request for a selected video program from the client device via the network interface 102 that has been previously bookmarked by the client device at a bookmark position. The command handler retrieves the selected video programs from the video source via the network interface 102 in response to the request. The command handler then generates and sends, via the network interface 102, an event playlist, such as segment playlist 250 to the client device having a plurality of event playlist segments, the plurality of event playlist segments including a last segment (represented by the link www.Morega.com/bwt000000N) that is based on the bookmark position, i.e. is at or slightly preceding the position that video player stopped, paused or otherwise bookmarked the video program. The event playlist lists the segments of the selected video up to the bookmark point. Because the segment playlist 250 is presented in the form of an event playlist, without a termination tag, this makes the video player at the client device believe that it is playing event in-progress. Said another way, the segment playlist 250 is formatted as a real-time event or other event in-progress—regardless of the fact that the video program may be a pre-recorded video program or other non-realtime event.

In response to seeing an event playlist, the video player at the client device automatically starts playback from the last segment on the list, without trying to request one or more initial segments of the video program. The video player of the client device generates a request for the last segment of the plurality of event playlist segments that is received via the network interface 102. In response, the streaming video server encodes and sends this last segment to the client device via the network interface and then sends, via the network interface 102, a full playlist 252 to the client device that includes a termination tag. This playlist contains all segments for the show from the first to the last, including the termination tag. In this case the client will not send any additional requests for playlist, as the last playlist contained the end of list flag. This avoids delays associated with the streaming server 50 or 50′ erroneously initializing at the beginning of the video program and then reinitializing at the bookmark position. It should be noted, that while playlist data 250 and 252 is shown in conjunction with FIGS. 10 and 11 in a particular format, other formats such as HLS format or other formats can likewise be employed.

FIG. 12 presents a block diagram representation of a client device 300 in accordance with an embodiment of the present invention. In particular a client device 300 such as client devices 60, 62, 64, 66, 68 or other device is presented for use in conjunction with a streaming video server, such as streaming video server 50 or 50′ or other streaming device.

Client device 300 includes a network interface 302 to bidirectionally communicate with streaming server 50 or 50′. The network interface 302 can include a modem, transceiver or other network interface adaptor for coupling to the streaming server 325 either directly or indirectly via a serial or parallel connection such as an Ethernet connection, Universal Serial Bus (USB) connection, an Institute of Electrical and Electronics Engineers (IEEE) 1394 (Firewire) connection, small computer serial interface (SCSI), high definition media interface (HDMI) connection or other wired connection that operates in accordance with either a standard or custom interface protocol. In addition or in the alternative, the network interface 302 can include a wireless link for coupling to the streaming server 325 either directly or indirectly through one or more devices that operate in accordance with a wireless network protocol such as 802.11a,b,g,n (referred to generically as 802.11x), Bluetooth, Ultra Wideband (UWB), 3G wireless data connection, 4G wireless data connection or other wireless connection that operates in accordance with either a standard or custom interface protocol. Client device 300 also includes a video decoder 304, a decryption device 306 and a video player 310 for selecting, decoding, decrypting and playing video programs via optional display device 315 or an external display that is coupled via a device interface that is not expressly shown. While certain elements of the client device 300 are shown, the client device may contain other elements.

The video player 310 operates in response to commands of a user received via a user interface such as a touch screen, remote control device or other device by generating a program request to the streaming server 50 or 50′ for a selected video program that is sent to the streaming server via the network interface 302. In addition, the client device 300 includes a client-side proxy 308, such as an HLS proxy server deployed on the client device.

The video decoder 304, video decryptor 306, client-side proxy 308 and video player 310 can be implemented via one or more processing devices and one or more memory devices. Such processing devices can include a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on operational instructions that are stored in a memory. The memory can include a hard disc drive or other disc drive, read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing device implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry.

FIG. 13 presents a block diagram representation of a client-side proxy device 308 in accordance with an embodiment of the present invention. One side of the client-side proxy 308 is connected to the remote streaming server, such as streaming video server 50 or 50. The other side of the client-side proxy is connected to the video player 310, such as an HLS player or other video player, via local HTTP connection. In this configuration the client-side proxy 308 is connected between the video player 310 and the streaming video server 50 or 50′ and communicates with each device via a device interface that emulates the other device. In this fashion, the client-side proxy 308 appears as a video player when communicating with the video server 50 or 50′ and appears as a video server 50 or 50′ when communicating with the video player 310. Commands, requests and data that pass through the client-side proxy can be identified and passed through, or translated, intercepted, held or otherwise modified.

The client-side proxy 308 can be used as an alternative to server side solution presented in conjunction with FIGS. 10 and 11 to handle bookmarks. In this mode of operation, the client-side proxy 308 passes the program request from the video player 310 to the streaming video server 50 or 50′ for a selected one of the plurality of video programs, while identifying that the selected video program has been previously bookmarked by the video player 308 at the bookmark position. In response, the client-side proxy intercepts any requests from the video player 310 to the streaming video server 50 or 50′ for any initial segment or segments of the selected video program. Instead of passing these requests to the streaming video server 50 or 50, the client-side proxy 308 sends a fixed segment or segments to the video player 310 to correspond with each such request. The fixed segment can be an empty segment, a single pre-stored segment or other fixed segment that is sent by the client-side proxy 308 to satisfy the request.

When the client-side proxy 308 receives a request from the video player 310 to the streaming video server 50 or 50′ for other segments commencing at a position in the video program corresponding to the bookmark position, these requests are passed by the client side proxy 308 to the streaming video server 50 or 50′. In this fashion, the client-side proxy 308 intercepts the requests for segments at the beginning of a playlist and returns fixed segments to the video player 310 in response, without sending the requests to the server. After the client-side proxy 308 receives requests at or near the bookmark position, it switches to pass-through mode and forwards all requests for segments from the video player 310 to the streaming server 50 or 50′. This offloads the bookmark processing from the server to the client device 300. It also avoids delays associated with the streaming server 50 or 50′ erroneously initializing at the beginning of the video program and then reinitializing at the bookmark position.

In an embodiment, the client-side proxy 308 identifies the initial segment or segments based on either their position at the beginning of the list or otherwise based on a comparison of their position to the bookmark position. In particular, the client-side proxy 308 can identify the initial segment or segments when the position these segments are either the first X positions of the playlist or when their position compares unfavorably to the bookmark position, by for example preceding the bookmark position by a time greater than Y.

In an embodiment, the client-side proxy 308 identifies the segments to pass based on a comparison of the position of these segments to the bookmark position. When the position of a requested segment favorably to the bookmark position, such as being at or slightly preceding the bookmark position, the request for the segment is passed to the streaming server 50 or 50′ along with requests for subsequent segments.

While the client-side proxy 308 was described above in a role of handling bookmarking, client-side proxy 308 can be used for other functions such as to efficiently implement event playlists. A user of client device 300 may be permitted to change a current position of playing video with a scroll bar of the video player 310 (hereinafter, “scrubbing”). One way to support scrubbing for shows being recorded is to use event playlists. As previously discussed, event playlists can require frequent transmission of the entire updated list. For this reason, these playlists can be difficult to implement in a streaming server 50 or 50′ due to the large amount of traffic required by these frequent updates.

In a further embodiment, the client-side proxy 308 can be used to communicate a different form of playlist data with the streaming server 50 or 50′ and to convert this playlist data to into event playlists that are sent to the video player 310. In operation, the client-side proxy 308 receives server playlist data corresponding to a selected video program from the streaming video server 50 or 50′. The client-side proxy 308 then generates proxy playlist data corresponding to the selected video program in response to the server playlist data that is sent to the video player 310, by translating the server playlist data from a first playlist format to a second playlist format of a streaming video protocol. In this fashion, sliding window playlist data of an HLS protocol, for example, from the streaming video server 50 can be converted into event playlist data of the HLS protocol. This can reduce the traffic in playlist data generated by the streaming server 50 or 50′.

This mode of operation of client-side proxy 308 can be described in conjunction with the following. The streaming server 50 or 50′ generates a first playlist that contains list of all available segments for the part of the video program that has been recorded up to the current point. This playlist does not contain a termination tag. The client side proxy 308 passes this playlist to the video player 310. This makes the video player 310 request the next playlist when all segments from the first playlist have been played. The streaming server 50 or 50′ switches to sliding window mode and generates small delta playlists for the content which was recorded since the last playlist was published. The client-side proxy 308 intercepts this additional server playlist data and produces local proxy playlist data in the form of full event playlists, which are communicated to the video player 310. At each step, the video player 310 has a complete playlist of segments that can be used to support scrubbing, however, the streaming server 50 or 50′ sends only playlist updates and is not burdened by sending full event playlists when requested by the video player.

This process can be further described in conjunction with the following example. Streaming server 50 or 50′ sends the following server playlist data for a video being recorded that are intercepted by the client-side proxy 308:

  Playlist #1 (event playlist) http://myserver.com?segid=100 http://myserver.com?segid=102 http://myserver.com?segid=103 http://myserver.com?segid=104 http://myserver.com?segid=105 Playlist #2 (sliding window playlist) http://myserver.com?segid=106 http://myserver.com?segid=107 Playlist #3 (sliding window playlist) http://myserver.com?segid=109 http://myserver.com?segid=110 #END-OF-LIST

In response, the client-side proxy generates the following proxy playlist data.

  a) http://localhost?segid=100 http://localhost?segid=102 http://localhost?segid=103 http://localhost?segid=104 http://localhost?segid=105 b) http://localhost?segid=100 http://localhost?segid=102 http://localhost?segid=103 http://localhost?segid=104 http://localhost?segid=105 http://localhost?segid=106 http://localhost?segid=107 c) http://localhost?segid=100 http://localhost?segid=102 http://localhost?segid=103 http://localhost?segid=104 http://localhost?segid=105 http://localhost?segid=106 http://localhost?segid=107 http://localhost?segid=109 http://localhost?segid=110 #END-OF-LIST

The client side-proxy operates to receive and store the corresponding segment data from the streaming video server 50 or 50′ locally. As shown, the client-side proxy accumulates the initial server playlist data and the updated sliding window playlist data to form event playlists that can be sent to the video player 310 with local addresses for each segment. Because the video player 310 is presented full event playlists and the segments are stored locally, user scrubbing can be supported directly by the client-side proxy 308. It should be noted, that while particular playlist data is presented in the examples described above, any format such as an HLS format or other formats can likewise be employed.

FIG. 14 presents a flowchart representation of a method in accordance with an embodiment of the present invention. In particular a method is shown for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-13. In step 400, playlist data corresponding to a plurality of video programs available from at least one video source are stored. Step 402 includes bidirectionally communicating with a client device and the at least one video source via a network interface. Step 404 includes receiving a request for a selected one of the plurality of video programs from the client device via the network interface that has been previously bookmarked by the client device at a bookmark position. Step 406 includes retrieving the selected one of the plurality of video programs from the at least one video source via the network interface in response to the request. Step 408 includes sending, via the network interface, an event playlist to the client device having a plurality of event playlist segments, the plurality of event playlist segments including a last segment that is based on the bookmark position. Step 410 includes receiving a request for the last segment of the plurality of event playlist segments from the client device via the network interface. Step 412 includes sending the last segment of the plurality of event playlist segments to the client device via the network interface. Step 414 includes sending, via the network interface, a full playlist to the client device after sending the last segment of the plurality of event playlist segments to the client device.

In an embodiment, the selected one of the plurality of video programs is a non-realtime event. The event playlist can be formatted in accordance with a realtime event. The full playlist can include a sequence of segments and a terminating tag. The last segment can have a position corresponding to the bookmark position or preceding the bookmark position. The method can further include encoding the last segment of the plurality of event playlist segments for transmission to the client device.

FIG. 15 presents a flowchart representation of a method in accordance with an embodiment of the present invention. In particular a method is shown for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-14. Step 430 includes passing a program request for a selected one of the plurality of video programs from a video player of the client device to a streaming video server. Step 432 includes identifying that the selected one of the plurality of video programs has been previously bookmarked by the video player at a bookmark position. Step 434 includes intercepting a request from the video player to the streaming video server for at least one first segment of the selected one of the plurality of video programs, and in response, sending at least one corresponding fixed segment to the video player. Step 436 includes passing a request from the video player to the streaming video server for a plurality of second segments of the selected one of the plurality of video programs, wherein the plurality of second segments commence at a position corresponding to the bookmark position.

In an embodiment, the at least one first segment of the selected one of the plurality of video programs is identified based on a comparison of a position of the at least one first segment and the bookmark position. The at least one first segment of the selected one of the plurality of video programs can be identified when the position of the at least one first segment compares unfavorably to the bookmark position. The plurality of second segments of the selected one of the plurality of video programs can be identified based on a comparison of a position of the at least one of the plurality of second segments and the bookmark position. The plurality of second segments of the selected one of the plurality of video programs can be identified when the position of the at least one of the plurality of second segments compares favorably to the bookmark position.

The at least one first segment can include a plurality of initial segments and the at least one corresponding fixed segment can include a single fixed segment that is sent to the video player in response to the request for each of the plurality of initial segments. The at least one corresponding fixed segment can be an empty segment.

FIG. 16 presents a flowchart representation of a method in accordance with an embodiment of the present invention. In particular a method is shown for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-15. Step 440 includes receiving server playlist data via a network interface of the client device, the server playlist data corresponding to the selected one of the plurality of video programs. Step 442 includes generating proxy playlist data based on the server playlist data via a client-side proxy, the proxy playlist data corresponding to the selected one of the plurality of video programs. Step 444 includes sending the proxy playlist data to a video player of the client device.

In an embodiment, the server playlist data includes first server playlist data corresponding including links to a first plurality of segments for the selected one of the plurality of video programs. The server playlist data can include second server playlist data corresponding including links to a second plurality of segments for the selected one of the plurality of video programs. The proxy playlist data can include at least one playlist that is generated based on the first server playlist data and the second server playlist data. The server playlist data includes at least one sliding window playlist. The proxy playlist data can include an event playlist generated based on the at least one sliding window playlist. The at least one sliding window playlist can include a plurality of sliding window playlists and the proxy playlist data includes an event playlist generated based on an accumulation of the plurality of sliding window playlists.

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “operable to” or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item. As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1.

As may also be used herein, the terms “processing module”, “processing circuit”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.

The present invention has been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claimed invention. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

The present invention may have also been described, at least in part, in terms of one or more embodiments. An embodiment of the present invention is used herein to illustrate the present invention, an aspect thereof, a feature thereof, a concept thereof, and/or an example thereof. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process that embodies the present invention may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.

Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.

The term “module” is used in the description of the various embodiments of the present invention. A module includes a processing module, a functional block, hardware, and/or software stored on memory for performing one or more functions as may be described herein. Note that, if the module is implemented via hardware, the hardware may operate independently and/or in conjunction software and/or firmware. As used herein, a module may contain one or more sub-modules, each of which may be one or more modules.

While particular combinations of various functions and features of the present invention have been expressly described herein, other combinations of these features and functions are likewise possible. The present invention is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. A client device comprising: a network interface, coupled to bidirectionally communicate with a streaming server via at least one network, wherein the streaming server stores server playlist data corresponding to a plurality of video programs available from at least one video source, the server playlist data including links to a plurality of segments for each of the plurality of video programs; a video player that generates a program request for a selected one of the plurality of video programs; a client-side proxy, coupled to the network interface and the video player and included in the client device, that is operable to receive the server playlist data corresponding to the selected one of the plurality of video programs, to generate proxy playlist data corresponding to the selected one of the plurality of video programs based on the server playlist data and to send the proxy playlist data to the video player, wherein the client-side proxy generates the proxy playlist data by translating the server playlist data from a sliding window playlist format to an event playlist format of a streaming video protocol without modifying the links to the plurality of segments.
 2. The client device of claim 1 wherein the server playlist data includes first server playlist data including links to a first plurality of segments for the selected one of the plurality of video programs.
 3. The client device of claim 2 wherein the server playlist data includes second server playlist data including links to a second plurality of segments for the selected one of the plurality of video programs.
 4. The client device of claim 3 wherein the proxy playlist data includes at least one playlist that is generated based on the first server playlist data and the second server playlist data.
 5. The client device of claim 1 wherein the server playlist data includes at least one sliding window playlist.
 6. The client device of claim 5 wherein the proxy playlist data includes an event playlist generated based on the at least one sliding window playlist.
 7. The client device of claim 5 wherein the at least one sliding window playlist includes a plurality of sliding window playlists and the proxy playlist data includes an event playlist generated based on an accumulation of the plurality of sliding window playlists.
 8. A method for use in a client device, the method comprising: receiving server playlist data via a network interface of the client device, the server playlist data corresponding to a selected one of a plurality of video programs, wherein the server playlist data includes first server playlist data including links to a first plurality of segments for the selected one of the plurality of video programs; generating proxy playlist data based on the server playlist data via a client-side proxy of the client device, the proxy playlist data corresponding to the selected one of the plurality of video programs, wherein the proxy playlist data is generated by translating the server playlist data from a sliding window playlist format to an event playlist format of a streaming video protocol without modifying the links to the first plurality of segments; and sending the proxy playlist data to a video player of the client device.
 9. The method of claim 8 wherein the server playlist data includes second server playlist data including links to a second plurality of segments for the selected one of the plurality of video programs.
 10. The method of claim 9 wherein the proxy playlist data includes at least one playlist that is generated based on the first server playlist data and the second server playlist data.
 11. The method of claim 8 wherein the server playlist data includes at least one sliding window playlist.
 12. The method of claim 11 wherein the proxy playlist data includes an event playlist generated based on the at least one sliding window playlist.
 13. The method of claim 11 wherein the at least one sliding window playlist includes a plurality of sliding window playlists and the proxy playlist data includes an event playlist generated based on an accumulation of the plurality of sliding window playlists. 